What To Do When Everything At Work Is Marked Urgent
At 9:12 on Monday, Anita and Bill opened the same inbox.
Same team, same manager, same five requests. Four of them said "urgent" somewhere in the subject line. One said "URGENT!!" twice.
Anita started at the top and worked down. Bill read all five first, then replied to one before touching anything.
By Friday, Anita had answered forty-one messages and finished nothing she could name. Bill had shipped the vendor analysis his manager had wanted since March.
Where their week split
Both of them worked hard. Both stayed late twice. The difference showed up in the first eleven minutes of Monday.
Anita read "urgent" as information about the task. Bill read it as information about the sender.
Ron Ashkenas wrote in Forbes about the fire-drill habit in offices. A sense of urgency, he noted, is sometimes a way of signalling importance or a reflection of personal anxiety. The word often describes the requester's week, not yours.
There is a mechanical problem too. A normal task relabeled as urgent jumps straight to the top of the queue. Do that five times, and the list stops working as a list.
Anita's Monday had five number-one priorities. That is another way of saying she had none.
Bill had one, plus four things with dates attached to them.
The sorting question
Ask one question before you touch anything marked urgent.
What actually happens if this lands Thursday?
Sometimes there is a real answer. A client presentation at 2pm, a payroll cutoff, a regulator with a filing date.
Those go first, and you should move fast on them.
Often there is no answer, because the sender never thought about a deadline. They typed "urgent" the way people type "hi."
Bill asks the question out loud when the answer is not obvious. He gets a real deadline about half the time. The vague half is his answer.
Asking does not make you look slow. It makes the sender do the thinking they skipped.
Two more sorting signals are worth learning. A request with a named date is usually real.
So is a request with a named person waiting on it. Everything else can be scheduled without anyone noticing.
Anita now writes the real deadline next to each task before she starts. Four of her five Monday requests had no date at all.
The push-back script
Pushing back sounds risky when you are new. It gets easier when you are not inventing the words in the moment. Copy these.
- When you need the real deadline: "Happy to take this on. When do you need it by, so I can slot it properly?"
- When two things collide: "I can do the vendor analysis today or the pricing deck today. Which one first?"
- When you already have a plan for it: "Got it. I'll have this to you Wednesday morning. Tell me if that's too late."
- When it genuinely does not fit: "I can't get to this before Thursday. Can it wait, or should it go to someone else?"
None of these say no. Each one hands the decision back to the person who owns the priority. That is usually your manager, and managers would far rather make that call than watch you guess.
Anita started using the second script in week three. Her manager reordered the list in about eight seconds, twice, with no drama at all.
Send these fast, within a few minutes of the request landing. A quick clarifying reply reads as engaged.
The same message sent two days later reads as an excuse. Speed is what makes a question feel like cooperation.
The one-thing rule
Pick one thing on Monday morning that has to be finished by Friday. Write it where you will see it on Wednesday, which is when the week starts eating itself.
Then protect the same ninety minutes every day for it. Same slot, blocked in your calendar, phone face down and out of reach.
Ninety minutes times five days is enough for most weekly deliverables. It is also short enough that nobody will fight you for it.
Everything else gets handled in the gaps around that block. Messages, small requests, the pricing question that lands at 4pm.
Bill's block is 9:30 to 11:00. He answers nothing inside it.
His manager knows, because he told her in a one-line message during his first week. "I'm keeping 9:30 to 11 for deep work, and I'll be on messages the rest of the day."
Nobody objected. Nobody usually does, because you are telling them when you are available, not when you are not.
If someone books over it, move the block to the afternoon that same day. A moved block still gets done.
A cancelled block becomes a habit within about two weeks. Bill has moved his eleven times this year and skipped it twice.
When the urgent request comes from your manager
Different rules apply, but only slightly.
You still ask for the deadline. You just attach the trade-off to it.
"Sure. That'll push the vendor analysis to Thursday. Is that okay?"
Now she has the whole picture, and she is choosing what to trade. Your calendar stops being something that happens to you.
Do this in writing when you can. A one-line message creates a record you can point at later, without anyone feeling accused.
Friday is the scoreboard
Anita changed one thing the following Monday. She read all five messages before replying to any of them.
Three of the four "urgent" ones turned out to be due the following week. One had no deadline at all. She finished the reporting template she had been carrying since February.
Your inbox will keep saying urgent. Friday is where you find out who was right.
